Method and unconstrained ue for communication of constrained ue with msgin5g server

ABSTRACT

The disclosure relates to a pre-5th-Generation (5G) or 5G communication system to be provided for supporting higher data rates Beyond 4th-Generation (4G) communication system such as Long Term Evolution (LTE). A method for communication of a constrained user equipment (UE) with a Message in Fifth Generation (MSGin5G) server providing a MSGin5G service in an IoT network is provided. The method includes receiving, by an unconstrained UE, a registration request comprises a security credential of the constrained UE from the constrained UE, where the unconstrained UE have access to the MSGin5G server and the constrained UE do not have access to the MSGin5G server. The method includes determining, by the unconstrained UE, whether the constrained UE is authorized based on the security credential. The method includes performing, by the unconstrained UE, a registration of the constrained UE with the unconstrained UE for communication of the constrained UE with the MSGin5G server based on authorization of the constrained UE.

CROSS-REFERENCE TO RELATED APPLICATION(S)

This application is based on and claims priority under 35 U.S.C. §119(a) of an Indian Provisional patent application number 202141001466,filed on Jan. 12, 2021, in the Indian Intellectual Property Office, andof an Indian Provisional patent application number 202141030562, filedon Jul. 7, 2021, in the Indian Intellectual Property Office, and of anIndian Complete patent application number 202141001466, filed on Dec. 8,2021, in the Indian Intellectual Property Office, the disclosure of eachof which is incorporated by reference herein in its entirety.

BACKGROUND 1. Field

The disclosure relates to wireless communication. More particularly, thedisclosure relates to a method and an unconstrained User Equipment (UE)for communication of a constrained UE with a Message in Fifth Generation(MSGin5G) server providing a MSGin5G service in an Internet-of-Things(IoT) network.

2. Description of Related Art

To meet the demand for wireless data traffic having increased sincedeployment of 4G (4^(th)-Generation) communication systems, efforts havebeen made to develop an improved 5G (5^(th)-Generation) or pre-5Gcommunication system. Therefore, the 5G or pre-5G communication systemis also called a ‘beyond 4G network’ or a ‘post Long Term Evolution(LTE) system’.

The 5G communication system is considered to be implemented in higherfrequency (millimeter (mm) Wave) bands, e.g., 60 GHz bands, so as toaccomplish higher data rates. To decrease propagation loss of the radiowaves and increase the transmission distance, the beamforming, massivemultiple-input multiple-output (MIMO), full dimensional MIMO (FD-MIMO),array antenna, an analog beam forming, large scale antenna techniquesare discussed in 5G communication systems.

In addition, in 5G communication systems, development for system networkimprovement is under way based on advanced small cells, cloud radioaccess networks (RANs), ultra-dense networks, device-to-device (D2D)communication, wireless backhaul, moving network, cooperativecommunication, coordinated multi-points (CoMP), reception-endinterference cancellation and the like.

In the 5G system, hybrid FSK and QAM modulation (FQAM) and slidingwindow superposition coding (SWSC) as an advanced coding modulation(ACM), and filter bank multi carrier (FBMC), non-orthogonal multipleaccess (NOMA), and sparse code multiple access (SCMA) as an advancedaccess technology have been developed.

3^(rd) Generation Partnership Project (3GPP) is currently defining amessaging service in a 5^(th) Generation (5G) system called as MSGin5Gservice for Massive Internet of Things (MIoT) devices. The MSGin5Gservice enables various message communication models with advancedmessaging service capabilities and performance over the 5G system. TheMSGin5G service is designed and optimized for MIoT device communicationincluding thing-to-thing communication and person-to-thingcommunication. Certain IoT devices such as sensors, activators, etc.usually have limitations in computation or storage or communication, anduse batteries or small solar photovoltaic equipment, called asconstrained UEs. Certain IoT devices such as a mobile, television,washing machine, refrigerator, etc. have advanced communicationcapabilities with sufficient storage, called as unconstrained UEs.

Existing systems for the MSgin5G service do not provide a method forexchange of messages between the constrained UEs and the unconstrainedUEs. Moreover, the constrained UEs generally need a gateway UserEquipment (UE) to communicate with a server. However, the existingsystems do not specify a method for identifying and forwarding areceived message to the constrained UE by the gateway UE upon receivingan MSGin5G message from the server. The constrained UEs support only lowcomputational protocols such as Constrained Application Protocol (CoAP)for communication, whereas the unconstrained UEs with advancedcapabilities use protocols such as Hyper-Text Transfer Protocol (HTTP)or Session Initiation Protocol (SIP) with more features support forcommunication. Due to using different communication protocols, atranslation of the messages from one protocol to another protocol isrequired between the constrained UEs and the unconstrained UEs to enablecommunication between such UEs, which is not provided by the existingsystems. Thus, it is desired to at least provide a useful alternative.

The above information is presented as background information only toassist with an understanding of the disclosure. No determination hasbeen made, and no assertion is made, as to whether any of the abovemight be applicable as prior art with regard to the disclosure.

SUMMARY

Aspects of the disclosure are to address at least the above-mentionedproblems and/or disadvantages and to provide at least the advantagesdescribed below. Accordingly, an aspect of the disclosure is to providea method and an unconstrained UE for communication of a constrained UEwith a MSGin5G server providing a MSGin5G service in an IoT network.

Another aspect of the disclosure is to enable/disable the unconstrainedUE as a message relay/gateway for the constrained UE for communicatingwith a messaging server based on a registration at the unconstrained UEeven without using a Universal Subscriber Identity Module (USIM) at theconstrained UE to connect to the messaging server.

Another aspect of the disclosure is to provide protocol translationwithin a messaging server for sending messages to the constrained UE viathe unconstrained UE that does not support the communication protocol ofthe constrained UE.

Another aspect of the disclosure is to provide an application layerinterface, i.e. MSGin5G-6 to enable application communication betweenthe constrained UE and the unconstrained UE while the unconstrained UEoperates as the message relay/gateway of the constrained UE.

Additional aspects will be set forth in part in the description whichfollows and, in part, will be apparent from the description, or may belearned by practice of the presented embodiments.

In accordance with an aspect of the disclosure, a method forcommunication of a constrained UE with a MSGin5G server providing aMSGin5G service in an IoT network is provided. The method includesreceiving, by an unconstrained UE, a registration request comprises asecurity credential of the constrained UE from the constrained UE, wherethe unconstrained UE has access to the MSGin5G server and theconstrained UE do not have access to the MSGin5G server, determining, bythe unconstrained UE, whether the constrained UE is authorized based onthe security credential, and performing, by the unconstrained UE, aregistration of the constrained UE with the unconstrained UE forcommunication of the constrained UE with the MSGin5G server based onauthorization of the constrained UE.

In an embodiment, the receiving, by the unconstrained UE, theregistration request comprises security credentials of the constrainedUE from the constrained UE, comprises identifying, by the constrainedUE, that the unconstrained UE is connected to the MSGin5G server, and,sending, by the constrained UE, the registration request comprises thesecurity credentials of the constrained UE to the unconstrained UE.

In an embodiment, the unconstrained UE and the constrained UEcommunicate each other through a MSGin5G-6 interface.

In an embodiment, the performing, by the unconstrained UE, theregistration of the constrained UE with the unconstrained UE forcommunication of the constrained UE with the MSGin5G server based onauthorization of the constrained UE, comprises determining, by theunconstrained UE, whether a local condition of the unconstrained UE tocommunicate with the MSGin5G server matches a threshold condition, andperforming, by the unconstrained UE, one of discarding the registrationrequest of the constrained UE, in response to determining that at leastone of the constrained UE is not authorized based on the securitycredential, and the local condition of the unconstrained UE does notmatch to the threshold condition, and registering the constrained UEwith the unconstrained UE by storing a mapping between information ofthe constrained UE and a layer-2 ID of the constrained UE, and enablinga gateway functionality of the unconstrained UE to operate theunconstrained UE as a gateway device for communication of theconstrained UE with the MSGin5G server, in response to determining thatthe constrained UE is authorized based on the security credential, andthe local condition of the unconstrained UE matches the thresholdcondition, and sending, by the unconstrained UE, a registration responseto the constrained UE.

In an embodiment, the information of constrained UE comprises anapplication Identity (ID) of an application client on the constrainedUE.

In an embodiment, the local condition comprises at least one of anavailable power at the unconstrained UE and a network connectivity toaccess the MSGin5G server.

In an embodiment, the sending, by the unconstrained UE, the registrationresponse to the constrained UE, comprises sending, by the unconstrainedUE, a registration success response to the constrained UE, in responseto registering the constrained UE with the unconstrained UE, andsending, by the unconstrained UE, a registration failure response to theconstrained UE, in response to discarding the registration request ofthe constrained UE.

In an embodiment, the method further includes receiving, by theunconstrained UE, a deregistration request from the constrained UE,where the constrained UE is registered to the unconstrained UE,performing, by the unconstrained UE, deregistration of the constrainedUE with the unconstrained UE by removing the mapping between theinformation of the constrained UE and the layer-2 ID of the constrainedUE, sending, by the unconstrained UE, a deregistration response to theconstrained UE, and includes disabling, by the unconstrained UE, thegateway functionality of the unconstrained UE when none of registereddevices are using the unconstrained device as the gateway device.

In an embodiment, the method further includes receiving, by theunconstrained UE, a request for sending a MSGin5G message to the MSGin5Gserver from the constrained UE, determining, by the unconstrained UE,whether the local condition of the unconstrained UE to communicate withthe MSGin5G server matches a threshold condition, performing, by theunconstrained UE, one of sending the MSGin5G message as one of apoint-to-point message and a group message to the MSGin5G server, inresponse to determining that the local condition of the unconstrained UEmatches the threshold condition, and discarding the request for sendingthe MSGin5G message to the MSGin5G server and sending a failure responseto the constrained UE, in response to determining that the localcondition of the unconstrained UE does not match to the thresholdcondition, and includes sending, by the unconstrained UE, a response ofsending the MSGin5G message to the constrained UE.

In an embodiment, the sending, by the unconstrained UE, the response ofsending the MSGin5G message to the constrained UE, comprises sending, bythe unconstrained UE, a success response of sending the MSGin5G messageto the constrained UE, in response to sending the MSGin5G message to theMSGin5G server and sending, by the unconstrained UE, a failure responseof sending the MSGin5G message to the constrained UE, in response todiscarding the request for sending the MSGin5G message to the MSGin5Gserver.

In an embodiment, the local condition comprises at least one ofavailable power at the unconstrained UE, network connectivity to accessthe MSGin5G server, a maximum allowed packet size of the MSGin5Gmessage.

In an embodiment, the method further includes receiving, by theunconstrained UE, a delivery report from the MSGin5G server, when adelivery status is enabled while sending the MSGin5G message to theMSGin5G server, and sending, by the unconstrained UE, the deliveryreport to the constrained UE.

In an embodiment, the method further includes receiving, by theunconstrained UE, one of a group message, a point-to-point message, andan application-to-point message from the MSGin5G server, performing, bythe unconstrained UE, reassembly of the received message when thereceived message is segmented, where the unconstrained UE performs asegment recovery of the received message when at least one segment ismissing in the received message, sending, by the unconstrained UE, aMSGin5G message received request to the constrained UE, where theMSGin5G message received request comprises an originator address, agroup ID, a payload of the received message, a delivery status, and apriority type, and receiving, by the unconstrained UE, a messagereceived response from the constrained UE when the MSGin5G messagereceived request is received at the constrained UE.

In an embodiment, the method further includes receiving, by theunconstrained UE, a message delivery status from the constrained UE,when a delivery status is enabled in the MSGin5G message receivedrequest and the MSGin5G message received request is received at theconstrained UE. The method includes sending, by the unconstrained UE, adelivery report to the MSGin5G server.

In accordance with another aspect of the disclosure, a method forcommunication of the constrained UE with the MSGin5G server providingthe MSGin5G service in the IoT network is provided. The method includesreceiving, by the unconstrained UE having access to the MSGin5G server,a registration request from the constrained UE, where the registrationrequest comprises the security credential required for the constrainedUE to register to the MSGin5G server, determining, by the unconstrainedUE, the local condition at the unconstrained UE for accepting orrejecting the received registration request, and performing, by theunconstrained UE, a registration for the constrained UE with the MSGin5Gserver when the registration request is accepted based on the localcondition.

In an embodiment, the local condition comprises at least one of anavailable power at the unconstrained UE, and a network connectivity toaccess the MSGin5G server.

In an embodiment, the method further includes accepting, by the MSGin5Gserver, the registration request from the unconstrained UE on behalf ofthe constrained UE based on the received security credential, andstoring, by the MSGin5G server, a mapping of the unconstrained UE actingas a gateway device to the constrained UE.

In an embodiment, the method further includes sending, by theunconstrained UE, a registration response message to the constrained UEindicating success or failure of the registration with the MSGin5Gserver, where the registration response message comprises a reason forregistration failure in case of the failure of the registration, wherethe registration response message comprises a MSGin5G service ID in caseof the success of the registration

In an embodiment, the unconstrained UE has capability to communicatewith the MSGin5G server, whereas the constrained UE do not havecapability to communicate with the MSGin5G server.

In an embodiment, the MSGin5G server includes a protocol conversionfunction to convert a first protocol format used for communication bythe unconstrained UE into a second protocol format used forcommunication by the constrained UE.

In an embodiment, the method further includes receiving, by theunconstrained UE, a request from the constrained UE for sending aMSGin5G message to the MSGin5G server, determining, by the unconstrainedUE, the local condition at the unconstrained UE for sending or rejectingthe received request for sending a MSGin5G message to the MSGin5Gserver, and sending, by the unconstrained UE, the MSGin5G message fromthe constrained UE to the MSGin5G server based on the local condition.

In an embodiment, the method further includes sending, by theunconstrained UE, a response message to the constrained UE indicates asuccessful transmission of the MSGin5G message to the MSGin5G server orrejection of the received request.

In an embodiment, the method further includes sending, by theunconstrained UE, a delivery report message to the constrained UEcomprising an indication of successfully receiving the MSGin5G messagefrom the constrained UE.

In an embodiment, the method further includes receiving, by theunconstrained UE, a request from the MSGin5G server to send a MSGin5Gmessage to the constrained UE, and sending, by the unconstrained UE, theMSGin5G message received from the MSGin5G server to the constrained UE.

In an embodiment, the method further includes sending, by theconstrained UE, a response message comprising acceptance or rejection ofthe MSGin5G message request to the MSGin5G server through theunconstrained UE.

In an embodiment, the method further includes sending, by theconstrained UE, a delivery report of the MSGin5G message to the MSGin5Gserver through the unconstrained UE.

In an embodiment, the MSGin5G message is a point-to-point message or agroup message.

In an embodiment, the method further includes receiving, by theunconstrained UE, a deregistration request from the constrained UE,where the constrained UE is registered, where the constrained UE isregistered with the MSGin5G server, performing, by the unconstrained UE,a deregistration for the constrained UE with the MSGin5G server, wherethe MSGin5G server removes the mapping of the unconstrained UE acting asthe gateway device to the constrained UE, receiving, by theunconstrained UE, a response from the MSGin5G server, and sending, bythe unconstrained UE, a response for the deregistration request to theconstrained UE indicating success or failure of the deregistration basedon the response received from the MSGin5G server.

In accordance with another aspect of the disclosure, an unconstrained UEfor communication of the constrained UE with the MSGin5G serverproviding the MSGin5G service in the IoT network is provided. Theunconstrained UE includes a memory, a processor, and a gatewaycontroller, coupled to the memory and the processor. The gatewaycontroller is configured to receive a registration request comprises asecurity credential of the constrained UE from the constrained UE, wherethe unconstrained UE has access to the MSGin5G server and theconstrained UE does not have access to the MSGin5G server, to determinewhether the constrained UE is authorized based on the securitycredential, and to perform a registration of the constrained UE with theunconstrained UE for communication of the constrained UE with theMSGin5G server based on the authorization of the constrained UE.

In accordance with another aspect of the disclosure, an unconstrained UEfor communication of the constrained UE with the MSGin5G serverproviding the MSGin5G service in the IoT network is provided. Theunconstrained UE includes the memory, the processor, and the gatewaycontroller, coupled to the memory and the processor. The gatewaycontroller is configured to receive the registration request from theconstrained UE, where the registration request comprises the securitycredential required for the constrained UE to register to the MSGin5Gserver. The gateway controller is configured for determining the localcondition at the unconstrained UE for accepting or rejecting thereceived registration request. The gateway controller is configured forperforming the registration for the constrained UE with the MSGin5Gserver when the registration request is accepted based on the localcondition.

Other aspects, advantages, and salient features of the disclosure willbecome apparent to those skilled in the art from the following detaileddescription, which, taken in conjunction with the annexed accompanyingdrawings, discloses various embodiments of the disclosure.

BRIEF DESCRIPTION OF THE DRAWINGS

The above and other aspects, features, and advantages of certainembodiments of the disclosure will be more apparent from the followingdescription taken in conjunction with the accompanying drawings, inwhich:

FIG. 1 illustrates an existing architecture of a system for providing aMSGin5G service, according to the related art;

FIG. 2 is a block diagram of an unconstrained UE for communication of aconstrained user equipment (UE) with a Message in Fifth Generation(MSGin5G) server for providing messages using the MSGin5G service,according to an embodiment of the disclosure;

FIG. 3 is a flow diagram illustrating a method for communication of theconstrained UE with the MSGin5G server by registering the constrained UEat the unconstrained UE according to an embodiment of the disclosure;

FIG. 4 is a flow diagram illustrating a method for communication of theconstrained UE with the MSGin5G server by registering the constrained UEat the MSGin5G server, according to an embodiment of the disclosure;

FIG. 5 illustrates a proposed architecture of the system for providingthe MSGin5G service, according to an embodiment of the disclosure;

FIG. 6 is a signaling diagram illustrating communication between theconstrained device, the unconstrained device, and the MSGin5G server forcommunicating a message using protocol translation, according to anembodiment of the disclosure;

FIG. 7 is a signaling diagram illustrating registration of theconstrained device with the MSGin5G server, according to an embodimentof the disclosure;

FIG. 8 is a signaling diagram illustrating deregistration of theconstrained device with the MSGin5G server, according to an embodimentof the disclosure;

FIG. 9 is a signaling diagram illustrating a scenario of sending apoint-to-point message to the MSGin5G server by the constrained device,according to an embodiment of the disclosure;

FIG. 10 is a signaling diagram illustrating a scenario of sending agroup message to the MSGin5G server by the constrained device, accordingto an embodiment of the disclosure;

FIG. 11 is a signaling diagram that illustrates a scenario of receivinga message from the MSGin5G server by the constrained device, accordingto an embodiment of the disclosure;

FIG. 12 is a signaling diagram illustrating registration of theconstrained device with the unconstrained device for using a gateway UEfunctionality, according to an embodiment of the disclosure; and

FIG. 13 is a signaling diagram illustrating deregistration of theconstrained device with the unconstrained device for discontinuing usageof the gateway functionality, according to an embodiment of thedisclosure.

The same reference numerals are used to represent the same elementsthroughout the drawings.

DETAILED DESCRIPTION

The following description with reference to the accompanying drawings isprovided to assist in a comprehensive understanding of variousembodiments of the disclosure as defined by the claims and theirequivalents. It includes various specific details to assist in thatunderstanding but these are to be regarded as merely exemplary.Accordingly, those of ordinary skill in the art will recognize thatvarious changes and modifications of the various embodiments describedherein can be made without departing from the scope and spirit of thedisclosure. In addition, descriptions of well-known functions andconstructions may be omitted for clarity and conciseness.

The terms and words used in the following description and claims are notlimited to the bibliographical meanings, but, are merely used by theinventor to enable a clear and consistent understanding of thedisclosure. Accordingly, it should be apparent to those skilled in theart that the following description of various embodiments of thedisclosure is provided for illustration purpose only and not for thepurpose of limiting the disclosure as defined by the appended claims andtheir equivalents.

It is to be understood that the singular forms “a,” “an,” and “the”include plural referents unless the context clearly dictates otherwise.Thus, for example, reference to “a component surface” includes referenceto one or more of such surfaces.

The embodiments herein and the various features and advantageous detailsthereof are explained more fully with reference to the non-limitingembodiments that are illustrated in the accompanying drawings anddetailed in the following description. Descriptions of well-knowncomponents and processing techniques are omitted so as to notunnecessarily obscure the embodiments herein. Also, the variousembodiments described herein are not necessarily mutually exclusive, assome embodiments can be combined with one or more other embodiments toform new embodiments. The term “or” as used herein, refers to anon-exclusive or, unless otherwise indicated. The examples used hereinare intended merely to facilitate an understanding of ways in which theembodiments herein can be practiced and to further enable those skilledin the art to practice the embodiments herein. Accordingly, the examplesshould not be construed as limiting the scope of the embodiments herein.

As is traditional in the field, embodiments may be described andillustrated in terms of blocks which carry out a described function orfunctions. These blocks, which may be referred to herein as managers,units, modules, hardware components or the like, are physicallyimplemented by analog and/or digital circuits such as logic gates,integrated circuits, microprocessors, microcontrollers, memory circuits,passive electronic components, active electronic components, opticalcomponents, hardwired circuits and the like, and may optionally bedriven by firmware. The circuits may, for example, be embodied in one ormore semiconductor chips, or on substrate supports such as printedcircuit boards and the like. The circuits constituting a block may beimplemented by dedicated hardware, or by a processor (e.g., one or moreprogrammed microprocessors and associated circuitry), or by acombination of dedicated hardware to perform some functions of the blockand a processor to perform other functions of the block. Each block ofthe embodiments may be physically separated into two or more interactingand discrete blocks without departing from the scope of the disclosure.Likewise, the blocks of the embodiments may be physically combined intomore complex blocks without departing from the scope of the disclosure.

The accompanying drawings are used to help easily understand varioustechnical features and it should be understood that the embodimentspresented herein are not limited by the accompanying drawings. As such,the disclosure should be construed to extend to any alterations,equivalents and substitutes in addition to those which are particularlyset out in the accompanying drawings. Although the terms first, second,etc. may be used herein to describe various elements, these elementsshould not be limited by these terms. These terms are generally onlyused to distinguish one element from another.

FIG. 1 illustrates an existing architecture of a system (1000A) forproviding a MSGin5G service, according to the related art.

Referring to FIG. 1, the existing architecture is defined as specifiedin a 3GPP Technical Report (TR) 23.700-24 V1.2.0. The MSGin5G serviceshall fulfil the service requirements which are enumerated in a 3GPPTechnical Specification (TS) 22.262. The system (1000A) includes aMSGin5G UE (10) which is an unconstrained UE, a non-3GPP UE (11)including a non-3GPP message client 11A, a legacy 3GPP UE (13), anapplication server (15), a MSGin5G server (16), a Service EnablerArchitecture Layer (SEAL) server (18). The application server (15) andthe MSGin5G server (16) communicate with each other via a MSGin5G-3interface. The SEAL server (18) and the MSGin5G server (16) communicatewith each other via a SEAL-S interface specified for each SEAL service.A non-3GPP message gateway (12) connects the non-3GPP UE (11) to theMSGin5G server (16) over a 3GPP network (14) via a MSGin5G-4 interface.A legacy 3GPP message gateway (17) connects the legacy 3GPP UE (13) tothe MSGin5G server (16) over the 3GPP network (14) via a MSGin5G-2interface.

The MSGin5G UE (10) includes an application client (10A), a MSGin5Gclient (10B), and a SEAL client (10C), where the application client(10A) and the MSGin5G client (10B) communicate each other via aMSGin5G-5 interface, and the MSGin5G client (10B) and the SEAL client(10C) communicate each other via a SEAL-C interface specified for eachSEAL service. The MSGin5G client (10B) and the MSGin5G server (16)communicate with each other over the 3GPP network (14) via a MSGin5G-1interface. A SEAL client (10C) and the SEAL server (18) communicate witheach other over the 3GPP network (14) via a SEAL-UU interface asspecified in a 3GPP TS 23.434. The 3GPP network and the SEAL server (18)communicate with each other via a network interface.

Throughout this disclosure, the terms “messaging server”, and “MSGin5Gserver” are used interchangeably and mean the same. Throughout thisdisclosure, the terms “interface”, and “reference point” are usedinterchangeably and mean the same. Throughout this disclosure, the terms“unconstrained UE (100)”, and “MSGin5G UE (100)” are usedinterchangeably and mean the same. Throughout this disclosure, the terms“constrained UE (200)”, and “MSGin5G UE (200)” are used interchangeablyand mean the same.

Accordingly, the embodiments herein provide a method for communicationof a constrained UE with a MSGin5G server providing a MSGin5G service inan IoT network. The method includes receiving, by an unconstrained UE, aregistration request comprises a security credential of the constrainedUE from the constrained UE, where the unconstrained UE has access to theMSGin5G server and the constrained UE do not have access to the MSGin5Gserver. The method includes determining, by the unconstrained UE,whether the constrained UE is authorized based on the securitycredential. The method includes performing, by the unconstrained UE, aregistration of the constrained UE with the unconstrained UE forcommunication of the constrained UE with the MSGin5G server based onauthorization of the constrained UE.

Accordingly, the embodiments herein provide a method for communicationof the constrained UE with the MSGin5G server providing the MSGin5Gservice in the IoT network. The method includes receiving, by theunconstrained UE having access to the MSGin5G server, a registrationrequest from the constrained UE, where the registration requestcomprises the security credential required for the constrained UE toregister to the MSGin5G server. The method includes determining, by theunconstrained UE, the local condition at the unconstrained UE foraccepting or rejecting the received registration request. The methodincludes performing, by the unconstrained UE, a registration for theconstrained UE with the MSGin5G server when the registration request isaccepted based on the local condition.

Accordingly, the embodiments herein provide the unconstrained UE forcommunication of the constrained UE with the MSGin5G server providingthe MSGin5G service in the IoT network. The unconstrained UE comprisinga memory, a processor, and a gateway controller, coupled to the memoryand the processor. The gateway controller is configured for receiving aregistration request comprises a security credential of the constrainedUE from the constrained UE, where the unconstrained UE have access tothe MSGin5G server and the constrained UE do not have access to theMSGin5G server. The gateway controller is configured for determiningwhether the constrained UE is authorized based on the securitycredential. The gateway controller is configured for performing aregistration of the constrained UE with the unconstrained UE forcommunication of the constrained UE with the MSGin5G server based onauthorization of the constrained UE.

Accordingly, the embodiments herein provide the unconstrained UE forcommunication of the constrained UE with the MSGin5G server providingthe MSGin5G service in the IoT network. The unconstrained UE comprisingthe memory, the processor, and the gateway controller, coupled to thememory and the processor. The gateway controller is configured forreceiving the registration request from the constrained UE, where theregistration request comprises the security credential required for theconstrained UE to register to the MSGin5G server. The gateway controlleris configured for determining the local condition at the unconstrainedUE for accepting or rejecting the received registration request. Thegateway controller is configured for performing the registration for theconstrained UE with the MSGin5G server when the registration request isaccepted based on the local condition.

Unlike existing methods and systems, the unconstrained UE canenable/disable its message relay/gateway functionality that controlscommunication between the constrained UE and the messaging server evenwithout using a Universal Subscriber Identity Module (USIM) at theconstrained UE to connect to the messaging server, based on aregistration of the constrained UE at the unconstrained UE. Therefore,resources of the unconstrained UE can be efficiently utilized bycontrolling an access of the unconstrained UE over the resources.

Unlike existing methods and systems, the proposed method allows protocoltranslation within the messaging server for sending messages to theconstrained UE via the unconstrained UE that does not support thecommunication protocol of the constrained UE, which enables seamlesscommunication between the constrained UE and the messaging server.

Unlike existing methods and systems, a proposed architecture of a systemfor providing the MSGin5G service includes an application layerinterface, i.e. MSGin5G-6 interface, to enable application communicationbetween the constrained UE and the unconstrained UE while theunconstrained UE operates as a message relay/gateway device of theconstrained UE.

Referring now to the drawings, and more particularly to FIGS. 2 through13, there are shown preferred embodiments.

FIG. 2 is a block diagram of an unconstrained UE (100) for communicationof a constrained UE (200) with a MSGin5G server (16) for providingmessages using the MSGin5G service, according to an embodiment of thedisclosure.

Referring to FIG. 2, an electronic device that has limitation incomputation and storage, and use batteries or small solar photovoltaicequipment, is called a constrained UE (200). Examples of the constrainedUE (200) include, but not limited to sensors, activators, etc. Anelectronic device that has advanced communication capabilities withsufficient storage, called as the unconstrained UE (100). Examples ofthe unconstrained UE (100) include, but not limited to a smartphone, atablet computer, a personal digital assistance (PDA), a desktopcomputer, an IoT device, etc. The unconstrained UE (100) have access tothe MSGin5G server (16) and the constrained UE (200) do not have accessto the MSGin5G server (16). i.e. the unconstrained UE (100) cancommunicate with the MSGin5G server (16), whereas the constrained UE(200) cannot communicate with the MSGin5G server (16). In an embodiment,the unconstrained UE (100) and the constrained UE (200) communicate witheach other through a MSGin5G-6 interface. In an embodiment, the MSGin5Gserver (16) includes a protocol conversion function to convert a firstprotocol format used for communication by the unconstrained UE (100)into a second protocol format used for communication by the constrainedUE (200).

Referring to FIG. 2, in an embodiment, the unconstrained UE (100)includes a gateway controller (110), a memory (120), a processor (130),and a communicator (140). The gateway controller (110) is implemented byprocessing circuitry such as logic gates, integrated circuits,microprocessors, microcontrollers, memory circuits, passive electroniccomponents, active electronic components, optical components, hardwiredcircuits, or the like, and may optionally be driven by a firmware. Thecircuits may, for example, be embodied in one or more semiconductorchips, or on substrate supports such as printed circuit boards and thelike.

The constrained UE (200) identifies that the unconstrained UE (100) isconnected to the MSGin5G server (16). Further, the constrained UE (200)sends a registration request comprises security credentials of theconstrained UE (200) to the unconstrained UE (100). The gatewaycontroller (110) receives a registration request comprises the securitycredential of the constrained UE (200) from the constrained UE (200).The gateway controller (110) determines whether the constrained UE (200)is authorized based on the security credential. The gateway controller(110) performs a registration of the constrained UE (200) with theunconstrained UE (100) for communication of the constrained UE (200)with the MSGin5G server (16) based on authorization of the constrainedUE (200).

In an embodiment, the gateway controller (110) determines whether alocal condition of the unconstrained UE (100) to communicate with theMSGin5G server (16) matches a threshold condition. In an embodiment, thelocal condition comprises an available power at the unconstrained UE(100) and/or a network connectivity to access the MSGin5G server (16).The gateway controller (110) discards the registration request of theconstrained UE (200), in response to determining that at least one ofthe constrained UE (200) is not authorized based on the securitycredential, and the local condition of the unconstrained UE (100) doesnot match to the threshold condition. The gateway controller (110)registers the constrained UE (200) with the unconstrained UE (100) bystoring a mapping between information of the constrained UE (200) and alayer-2 ID of the constrained UE (200), and enabling a gatewayfunctionality of the unconstrained UE (100) to operate the unconstrainedUE (100) as a gateway device for communication of the constrained UE(200) with the MSGin5G server (16), in response to determining that theconstrained UE (200) is authorized based on the security credential, andthe local condition of the unconstrained UE (100) matches the thresholdcondition. An example for the information of the constrained UE (200) isan application Identity (ID) of an application client (20A) on theconstrained UE (200).

The gateway controller (110) sends a registration response to theconstrained UE (200). In an embodiment, the gateway controller (110)sends a registration success response to the constrained UE (200), inresponse to registering the constrained UE (200) with the unconstrainedUE (100). In an embodiment, the gateway controller (110) sends aregistration failure response to the constrained UE (200), in responseto discarding the registration request of the constrained UE (200).

Upon registering the constrained UE (200) to the unconstrained UE (100),the gateway controller (110) may receive a deregistration request fromthe constrained UE (200) when the constrained UE (200) wants todiscontinue the registration at the unconstrained UE (100). The gatewaycontroller (110) performs a deregistration of the constrained UE (200)with the unconstrained UE (100) by removing the mapping between theinformation of the constrained UE (200) and the layer-2 ID of theconstrained UE (200). The gateway controller (110) sends aderegistration response to the constrained UE (200) and disables thegateway functionality of the unconstrained UE (100) when none ofregistered devices are using the unconstrained device as a gatewaydevice.

Upon registering the constrained UE (200) to the unconstrained UE (100),the gateway controller (110) may receive a request for sending a MSGin5Gmessage to the MSGin5G server (16) from the constrained UE (200).Further, the gateway controller (110) determines whether the localcondition of the unconstrained UE (100) to communicate with the MSGin5Gserver (16) matches the threshold condition. In another embodiment, thelocal condition comprises the available power at the unconstrained UE(100), and/or the network connectivity to access the MSGin5G server(16), and/or a maximum allowed packet size of the MSGin5G message. Thegateway controller (110) sends the MSGin5G message as one of apoint-to-point message and a group message to the MSGin5G server (16),in response to determining that the local condition of the unconstrainedUE (100) matches the threshold condition. The gateway controller (110)discards the request for sending the MSGin5G message to the MSGin5Gserver (16), and sends a registration failure response to theconstrained UE (200), in response to determining that the localcondition of the unconstrained UE (100) does not match to the thresholdcondition.

The gateway controller (110) sends a response of sending the MSGin5Gmessage to the constrained UE (200). In an embodiment, the gatewaycontroller (110) sends a success response of sending the MSGin5G messageto the constrained UE (200), in response to sending the MSGin5G messageto the MSGin5G server (16). In another embodiment, the gatewaycontroller (110) sends a failure response of sending the MSGin5G messageto the constrained UE (200), in response to discarding the request forsending the MSGin5G message to the MSGin5G server (16).

Upon sending the response of sending the MSGin5G message to theconstrained UE (200), the gateway controller (110) may receive adelivery report from the MSGin5G server (16), when a delivery status isenabled while sending the MSGin5G message to the MSGin5G server (16).Further, the gateway controller (110) sends the delivery report to theconstrained UE (200).

Upon registering the constrained UE (200) to the unconstrained UE (100),the gateway controller (110) may receive one of a group message, apoint-to-point message, and an application-to-point message from theMSGin5G server (16). Further, the gateway controller (110) performs areassembly of the received message when the received message issegmented, where the unconstrained UE (100) performs a segment recoveryof the received message when at least one segment is missing in thereceived message. Further, the gateway controller (110) sends a MSGin5Gmessage received request to the constrained UE (200), where the MSGin5Gmessage received request comprises an originator address, a group ID, apayload of the received message, a delivery status, and a priority type.Further, the gateway controller (110) receives a message receivedresponse from the constrained UE (200) when the MSGin5G message receivedrequest is received at the constrained UE (200). Further, the gatewaycontroller (110) may receive a message delivery status from theconstrained UE (200), when a delivery status is enabled in the MSGin5Gmessage received request and the MSGin5G message received request isreceived at the constrained UE (200). Further, the gateway controller(110) sends a delivery report to the MSGin5G server (16).

In another embodiment, the gateway controller (110) receives aregistration request from the constrained UE (200), where theregistration request comprises the security credential required for theconstrained UE (200) to register to the MSGin5G server (16). Further,the gateway controller (110) determines the local condition at theunconstrained UE (100) for accepting or rejecting the receivedregistration request. Further, the gateway controller (110) performsregistration for the constrained UE (200) with the MSGin5G server (16)when the registration request is accepted based on the local condition.Further, the MSGin5G server (16) accepts the registration request fromthe unconstrained UE (100) on behalf of the constrained UE (200) basedon the received security credential. Further, the MSGin5G server (16)stores a mapping of the unconstrained UE (100) acting as the gatewaydevice to the constrained UE (200).

Upon registering the constrained UE (200) with the MSGin5G server (16),the gateway controller (110) may send a registration response message tothe constrained UE (200) indicating success or failure of theregistration with the MSGin5G server (16), where the registrationresponse message comprises a reason for registration failure in case ofthe failure of the registration, and the registration response messagecomprises a MSGin5G service ID in case of the success of theregistration.

Upon registering the constrained UE (200) with the MSGin5G server (16),the gateway controller (110) may receive a request from the constrainedUE (200) for sending a MSGin5G message to the MSGin5G server (16), wherethe MSGin5G message is one of a point-to-point message or a groupmessage. Further, the gateway controller (110) determines the localcondition at the unconstrained UE (100) for sending or rejecting thereceived request to the MSGin5G server (16). Further, the gatewaycontroller (110) sends the MSGin5G message from the constrained UE (200)to the MSGin5G server (16) based on the local condition. Further, thegateway controller (110) sends a response message to the constrained UE(200) indicates a successful transmission of the MSGin5G message to theMSGin5G server (16) or rejection of the received request. Further, thegateway controller (110) sends a delivery report message to theconstrained UE (200) comprising an indication of successfully receivingthe MSGin5G message from the constrained UE (200).

Upon registering the constrained UE (200) with the MSGin5G server (16),the gateway controller (110) may receive a request from the MSGin5Gserver (16) to send a MSGin5G message to the constrained UE (200).Further, the gateway controller (110) sends the MSGin5G message receivedfrom the MSGin5G server (16) to the constrained UE (200). Further, theconstrained UE (200) sends a response message comprising acceptance orrejection of the MSGin5G message request to the MSGin5G server (16)through the unconstrained UE (100). Further, the constrained UE (200) adelivery report of the MSGin5G message to the unconstrained UE (100).

Upon registering the constrained UE (200) with the MSGin5G server (16),the gateway controller (110) may receive a deregistration request fromthe constrained UE (200). Further, the gateway controller (110) performsderegistration for the constrained UE (200) with the MSGin5G server(16), where the MSGin5G server (16) removes the mapping of theunconstrained UE (100) acting as the gateway device to the constrainedUE (200). Further, the gateway controller (110) receives a response fromthe MSGin5G server (16). Further, the gateway controller (110) sends aresponse for the deregistration request to the constrained UE (200)indicating success or failure of the deregistration based on theresponse received from the MSGin5G server (16).

The memory (120) stores mapping of the security credential, and mappingof the unconstrained UE (100) acting as the gateway device to theconstrained UE (200). The memory (120) stores instructions to beexecuted by the processor (130). The memory (120) may includenon-volatile storage elements. Examples of such non-volatile storageelements may include magnetic hard discs, optical discs, floppy discs,flash memories, or forms of electrically programmable memories (EPROM)or electrically erasable and programmable (EEPROM) memories. Inaddition, the memory (120) may, in some examples, be considered anon-transitory storage medium. The term “non-transitory” may indicatethat the storage medium is not embodied in a carrier wave or apropagated signal. However, the term “non-transitory” should not beinterpreted that the memory (120) is non-movable. In some examples, thememory (120) can be configured to store larger amounts of informationthan its storage space. In certain examples, a non-transitory storagemedium may store data that can, over time, change (e.g., in RandomAccess Memory (RAM) or cache). The memory (120) can be an internalstorage unit or it can be an external storage unit of the unconstrainedUE (100), a cloud storage, or any other type of external storage. In anembodiment, an application client (10A), a MSGin5G client (10B), and aSEAL client (10C) of the unconstrained UE (100) is residing in thememory (120), where the gateway controller (110) is configured forperforming the proposed operations using at least one of the applicationclient (10A), the MSGin5G client (10B), and the SEAL client (10C).

The processor (130) is configured to execute instructions stored in thememory (120). The processor (130) may be a general-purpose processor,such as a Central Processing Unit (CPU), an Application Processor (AP),or the like, a graphics-only processing unit such as a GraphicsProcessing Unit (GPU), a Visual Processing Unit (VPU) and the like. Theprocessor (130) may include multiple cores to execute the instructions.The communicator (140) is configured for communicating internallybetween hardware components in the unconstrained UE (100). Further, thecommunicator (140) is configured to facilitate the communication betweenthe unconstrained UE (100) and other devices (e.g., constrained UE(200), MSGin5G server (16)) via one or more networks (e.g., Radiotechnology). The communicator (140) includes an electronic circuitspecific to a standard that enables wired or wireless communication.

Although FIG. 2 shows the hardware components of the unconstrained UE(100) but it is to be understood that other embodiments are not limitedthereon. In other embodiments, the unconstrained UE (100) may includeless or more components. Further, the labels or names of the componentsare used only for illustrative purpose and does not limit the scope ofthe disclosure. One or more components can be combined together toperform same or substantially similar function for communication of theconstrained UE (200) with the MSGin5G server (16).

FIG. 3 is a flow diagram (300) illustrating a method for communicationof the constrained UE (200) with the MSGin5G server (16) by registeringthe constrained UE (200) at the unconstrained UE (100), according to anembodiment of the disclosure.

Referring to FIG. 3, in an embodiment, the method allows the gatewaycontroller (110) to perform operations 301 through 304 of the flowdiagram (300). At operation 301, the method includes receiving theregistration request comprises the security credential of theconstrained UE (200) from the constrained UE (200), where theunconstrained UE (100) have access to the MSGin5G server (16) and theconstrained UE (200) do not have access to the MSGin5G server (16). Atoperation 302, the method includes determining the local condition atthe unconstrained UE (100) for accepting or rejecting the receivedregistration request. At operation 303, the method includes determiningwhether the constrained UE (200) is authorized based on the securitycredential. At operation 304, the method includes performing theregistration of the constrained UE (200) with the unconstrained UE (100)for communication of the constrained UE (200) with the MSGin5G server(16) based on authorization of the constrained UE (200) and the localcondition.

FIG. 4 is a flow diagram (400) illustrating a method for communicationof the constrained UE (200) with the MSGin5G server (16) by registeringthe constrained UE (200) at the MSGin5G server (16), according to anembodiment of the disclosure.

Referring to FIG. 4, in an embodiment, the method allows the gatewaycontroller (110) to perform operations 401-403 of the flow diagram(400). At operation 401, the method includes receiving the registrationrequest from the constrained UE (200), where the registration requestcomprises the security credential required for the constrained UE (200)to register to the MSGin5G server (16). At operation 402, the methodincludes determining the local condition at the unconstrained UE (100)for accepting or rejecting the received registration request. Atoperation 403, the method includes performing the registration for theconstrained UE (200) with the MSGin5G server (16) when the registrationrequest is accepted based on the local condition.

The various actions, acts, blocks, operations, or the like in the flowdiagrams (300, 400) may be performed in the order presented, in adifferent order or simultaneously. Further, in some embodiments, some ofthe actions, acts, blocks, operations, or the like may be omitted,added, modified, skipped, or the like without departing from the scopeof the disclosure.

FIG. 5 illustrates a proposed architecture of the system (1000B) forproviding the MSGin5G service, according to an embodiment of thedisclosure.

Referring to FIG. 5, in addition to the system (1000A) described in theFIG. 1, the proposed system (1000B) contains the MSGin5G UE (200) thatdoes not have enough capability to communicate with the MSGin5G server(16). The MSGin5G UE (100) has advanced capabilities and can communicatewith the MSGin5G server (16) over the MSGin5G-1 interface. In anembodiment, the MSGin5G UE (200) includes an application client (20A), aMSGin5G client (20B), and a SEAL client (20C). The application client(20A) and the MSGin5G client (20B) communicate each other using aMSGin5G-5 interface. The SEAL client (20C) and the MSGin5G client (20B)communicate with each other using a SEAL-C interface. The MSGin5G client(20B) and the MSGin5G client (10B) communicate with each other throughthe MSGin5G-6 interface for enabling/disabling the MSGin5G UE (100) asthe gateway device for the MSGin5G UE (200). The SEAL client (20C) andthe SEAL client (10C) communicate with each other through the SEAL-PCSinterface.

If allowed by configuration, the MSGin5G UE (100) operates as themessage gateway device to the MSGin5G UE (200). In certain deploymentoptions, a group management function based on a SEAL group managementserver specified in 3GPP TS 23.434 can be implemented in the MSGin5Gserver (16). The MSGin5G service supports both the MSGin5G UEs (100,200). Both the MSGin5G UEs (100, 200) may support different protocols. Aprotocol conversion function of the Msgin5G server (16) converts oneprotocol format (e.g. CoAP) into another protocol format (e.g. HTTP) orvice versa.

FIG. 6 is a signaling diagram illustrating communication between theconstrained device (200), the unconstrained UE (100), and the MSGin5Gserver (16) for communicating a message using protocol translation,according to an embodiment of the disclosure.

Referring to FIG. 6, consider, the MSGin5G UE (100) is connected to anaccess network (i.e. the IoT network) that provides connectivity to theMSGin5G server (16). The MSGin5G UE (200) does not have a connection tothe access network that provides connectivity to the MSGin5G server(16). The MSGin5G client (20B) has been configured with the MSGin5Gserver identity. The MSGin5G server (16) has been configured withnecessary credentials to enable authenticating the MSGin5G client (20B).The MSGin5G UE (200) has discovered the MSGin5G UE (100) havingconnectivity to the MSGin5G server (16), and have mutually authenticatedeach other. At operation 601, the MSGin5G UE (200) communicates with theMSGin5G UE (100) to register with the MSGin5G server (16), and furtherto send or receive point-to-point, group, point-to-application, orapplication-to-point messages. At operation 602, the MSGin5G UE (100)sends the received message to the MSGin5G server (16) as specified in3GPP TS 23.554. At operation 603, the MSGin5G server (16) checks thatintended recipient of the message requires a different protocol based onregistration information or any other available information, and thusperforms protocol conversion with help of the protocol conversionfunction. At operation 604, the MSGin5G server (16) sends the message tothe intended recipient as specified in 3GPP TS 23.554.

FIG. 7 is a signaling diagram illustrating registration of theconstrained device (200) with the MSGin5G server (16), according to anembodiment of the disclosure.

Referring to FIG. 7, the MSGin5G client (20B) is responsible fortriggering the registration to the MSGin5G server (16). The trigger forregistration is based on an application service logic. Consider, theMSGin5G UE (100) is connected to the access network that providesconnectivity to the MSGin5G server (16). The MSGin5G UE (200) does nothave a connection to the access network that provides connectivity tothe MSGin5G server (16). The MSGin5G client (20B) has been configuredwith the MSGin5G server identity. The MSGin5G server (16) has beenconfigured with the necessary credentials to enable authenticating theMSGin5G client (20B). The MSGin5G UE (200) has discovered the MSGin5G UE(100) having connectivity to the MSGin5G server (16), and have mutuallyauthenticated each other.

At operation 701, upon receiving a request from the application client(20A) on the MSGin5G UE (200) to register with the MSGin5G server (16),the MSGin5G client (20B) sends the MSGin5G request for registration tothe MSGin5G client (10B). The request includes security credentialsrequired for the MSGin5G client (20B) to register to the MSGin5G server(16). Information elements in the request are given in Table 1.

TABLE 1 MSGin5G request for registration message Information elementStatus Description UE ID M Identity of the UE hosting the MSGin5G client(e.g., the external identifier defined in TS 23.682 [x], or a MobileStation Integrated Services Digital Network (MSISDN)) MSGin5G O A listof the MSGin5G capabilities supported client by the MSGin5G client(e.g., Mobile capabilities Originated Mobile Terminated (MOMT) (i.e.,point-to-point message), Application Oriented Mobile Terminated (AOMT)(i.e., application-to-point message), Mobile Originated, ApplicationTerminated (MOAT) (i.e., point-to-application message, Group, Broadcast)MSGin5G O MSGin5G client identifier assigned to the service ID MSGin5Gclient by the MSGin5G server upon initial registration. This element isadded while performing registration update. AS service ID M Identity ofthe MSGin5G server to which the 5GMSGS client (20B) intends to register.

At operation 702, upon receiving the request from the MSGin5G client(20B), the MSGin5G client (10B) may reject the MSGin5G request forregistration based on the local condition (like available power orconnectivity to access network or any other reason outside the scope of3GPP). If the MSGin5G client (10B) decides to reject the MSGin5G requestfor the registration message, then the MSGin5G client (10B) performsoperation 703. Otherwise, the MSGin5G client (10B) performs theregistration procedure as specified in clause 8.2.1 of 3GPP TS 23.554,with the following clarification and additional information elementsdefined in Table 2.

TABLE 2 Additional information for MSGin5G Client Registration requestInformation element Status Description MSGin5G service ID of the OMSGin5G client identifier of the UE acting as a message MSGin5G client(10B) who sends gateway UE registration request for MSGin5G client(20B).

The UE ID in the MSGin5G client registration request is set to UE IDreceived in the MSGin5G request for registration message. The MSGin5Gclient capabilities in the MSGin5G client registration request is set tothe MSGin5G client capabilities received in the request for registrationmessage. The MSGin5G client (10B) may decide to use different clientports other than the ports used in its own registration request. TheMSGin5G server (16) accepts the registration request from the MSGin5Gclient (10B) on behalf of the MSGin5G client (20B) based on the securitycredentials provided in the registration request message, and furtherupon successful registration stores the mapping where the MSGin5G client(10B) acting as the message gateway device to the MSGin5G client (20B).The mapping will be used while sending the message to the MSGin5G client(20B).

At operation 703, upon deciding the reject the request for registrationmessage in the operation 702 or upon receiving a response from MSGin5Gserver (16), the MSGin5G client (10B) sends a MSGin5G response forregistration message to the MSGin5G client (20B) indicating success orfailure of the registration. In case of successful registration, theMSGin5G client (10B) includes the MSGin5G service ID assigned by theMSGin5G server (16) to the MSGin5G client (20B). In case of failure, theMSGin5G client (10B) includes a reason for the failure in thenotification message. The MSGin5G client (10B) may act as a relay formultiple constrained devices. The MSGin5G client (10B) needs to maintaina mapping between the UE ID, and the AS server ID, and the MSGin5Gservice ID of the device initiated the request.

FIG. 8 is a signaling diagram illustrating the deregistration of theconstrained device with the MSGin5G server (16), according to anembodiment of the disclosure.

Referring to FIG. 8, the MSGin5G client (20B) is responsible fortriggering the deregistration to the MSGin5G server (16). The triggerfor deregistering is based on the application service logic. Consider,the MSGin5G UE (100) is connected to the access network that providesconnectivity to the MSGin5G server (16). The MSGin5G UE (200) does nothave a connection to the access network that provides connectivity tothe MSGin5G server (16). The MSGin5G server (16) has been configuredwith the necessary credentials to enable authenticating the MSGin5Gclient (20B). The MSGin5G UE (200) has discovered the MSGin5G UE (100)having connectivity to the MSGin5G server (16), and have mutuallyauthenticated each other. The MSGin5G client (20B) has been registeredwith the MSGin5G server (16) using the MSGin5G UE (100) as the messagegateway device.

At operation 801, upon receiving a request from the application client(20A) on the MSGin5G UE (200) to deregister with the MSGin5G server(16), the MSGin5G client (20B) sends a MSGin5G request forderegistration message to the MSGin5G client (10B). Information elementsin the request are defined in Table 3.

TABLE 3 MSGin5G request for deregistration message Information elementStatus Description MSGin5G service ID M MSGin5G client identifierassigned to the MSGin5G client by the MSGin5G server upon initialregistration.

At operation 802, upon receiving the request from the MSGin5G client(20B), the MSGin5G client (10B) performs the deregistration procedure asspecified in clause 8.2.1 of 3GPP TS 23.554. The MSGin5G server (16)removes the mapping where the MSGin5G client (10B) acts as the messagegateway device to the MSGin5G client (20B). At operation 803, uponreceiving a response from the MSGin5G server (16), the MSGin5G client(10B) sends a MSGin5G response for deregistration message to the MSGin5Gclient (10B) indicating success or failure of the deregistration.

FIG. 9 is a signaling diagram illustrating a scenario of sending thepoint-to-point message to the MSGin5G server (16) by the constraineddevice (200), according to an embodiment of the disclosure.

Referring to FIG. 9, consider, the MSGin5G UE (100) is connected to theaccess network that provides connectivity to the MSGin5G server (16).The MSGin5G UE (200) does not have a connection to the access networkthat provides connectivity to the MSGin5G server (16). The MSGin5Gclient (20B) has registered with the MSGin5G server (16) using MSGin5GUE (100) which is acting as the message gateway device. At operation901, upon receiving a request from the application client (20A) on theMSGin5G UE (200) to send the point-to-point message, the MSGin5G client(20B) sends a request to send the MSGin5G message to the MSGin5G client(10B). Information elements in the request to send MSGin5G message isgiven in table 8.3.2-1 of 3GPP TS 23.554.

At operation 902, upon receiving the request from the MSGin5G client(20B), the MSGin5G client (10B) may reject the request to send theMSGin5G message based on the local condition (like available power orconnectivity to access network or any other reason outside the scope of3GPP). If the MSGin5G client (10B) decides to reject the request, thenthe MSGin5G client (10B) decides to perform operation 903. Otherwise, ifthe size of the received message exceeds the maximum allowed packetsize, the MSGin5G client (10B) sends the point-to-point message asspecified in clause 8.5.4 of 3GPP TS 23.554. If the size of the receivedmessage does not exceed the maximum allowed packet size, then theMSGin5G client (10B) sends the point-to-point message as specified inthe clause 8.7.1.1 of 3GPP TS 23.554. The MSGin5G client (10B) uses theinformation elements received in request to send the MSGin5G messagerequest from the MSGin5G client (20B) to send the MSGin5G messagerequest with additional information elements defined in Table 4.

TABLE 4 Additional information for MSGin5G message request Informationelement Status Description MSGin5G service ID of UE O MSGin5G clientidentifier of the acting as a message gateway MSGin5G client (10B) whosends UE point-to-point message for MSGin5G client (20B).

At operation 903, the MSGin5G client (10B) sends a response to sendMSGin5G message to the MSGin5G client (20B). If the MSGin5G client (10B)has decided to reject the request to send the message in operation 902or the MSGin5G client (10B) received reject response from the MSGin5Gserver (16) in operation 902, then the MSGin5G client (10B) sends afailure response to the MSGin5G client (20B) and stops performingfurther operations. Otherwise, the MSGin5G client (10B) sends a successresponse to the MSGin5G client (20B). At 904, if the delivery status isenabled while sending the message, then the MSGin5G client (10B)receives the delivery report from the MSGin5G server (16). At operation905, upon receiving the delivery report, the MSGin5G client (10B) sendsthe delivery report to the MSGin5G client (20B).

FIG. 10 is a signaling diagram illustrating a scenario of sending thegroup message to the MSGin5G server (16) by the constrained device(200), according to an embodiment of the disclosure.

Referring to FIG. 10, consider, the MSGin5G UE (100) is connected to theaccess network that provides connectivity to the MSGin5G server (16).The MSGin5G UE (200) does not have a connection to the access networkthat provides connectivity to the MSGin5G server (16). The MSGin5Gclient (20B) has registered with the MSGin5G server (16) using theMSGin5G UE (100) which is operating as the message gateway device. AMSGin5G group is created by following group management SEAL serviceprocedures as specified in 3GPP TS 23.434, and the MSGin5G UE (200) is amember of the group.

At operation 1001, upon receiving a request from the application client(20A) on the MSGin5G UE (200) to send the group message, the MSGin5Gclient (20B) sends the request to send MSGin5G group message to theMSGin5G client (10B). The request includes the information elementsgiven in table 8.3.2-1 of 3GPP TS 23.554. At operation 1002, uponreceiving the request from the MSGin5G client (20B), the MSGin5G client(10B) may reject the request to send the MSGin5G message based on thelocal condition (like available power or connectivity to access networkor any other reason outside the scope of 3GPP). If the MSGin5G client(10B) decides to reject the request, then the MSGin5G client (10B)performs operation 1003. Otherwise, if the size of the received messageexceeds the maximum allowed packet size, the MSGin5G client (10B) sendsthe group message as specified in clause 8.5.5 of 3GPP TS 23.554. If thesize of the received message does not exceed the maximum allowed packetsize, the MSGin5G client (10B) sends the group message as specified inclause 8.7.4 of 3GPP TS 23.554. The 5GMSGS client (10B) uses theinformation elements received in the request to send the MSGin5G messagerequest from the MSGin5G client (20B) to send the MSGin5G messagerequest to the MSGin5G server (16) with additional information elementsdefined in Table 5.

TABLE 5 Additional information for MSGin5G message request Informationelement Status Description MSGin5G Service ID of UE O MSGin5G clientidentifier of the acting as a message gateway MSGin5G client (10B) whosends UE point-to-point message for MSGin5G client (20B)

At operation 1003, the MSGin5G client (10B) sends a response to sendMSGin5G group message to the MSGin5G client (20B). If the MSGin5G client(10B) has decided to reject the request to send the message in operation1002 or the MSGin5G client (10B) received reject response from theMSGin5G server (16) in operation 1002, the MSGin5G client (10B) sendsthe failure response to the MSGin5G client (20B) and stops performingfurther operations. Otherwise, the MSGin5G client (10B) sends thesuccess response to the MSGin5G client (20B). At operation 1004, if thedelivery status is enabled while sending the message, the MSGin5G client(10B) may receive the delivery report(s) from the MSGin5G server (16).At operation 1005, upon receiving the delivery report(s), the MSGin5Gclient (10B) sends the delivery report(s) to the MSGin5G client (20B).

FIG. 11 is a signaling diagram illustrates a scenario of receiving themessage from the MSGin5G server (16) by the constrained device (200),according to an embodiment of the disclosure. The message can be thegroup message or the point-to-point message or the point-to-applicationmessage.

Referring to FIG. 11, consider, the MSGin5G UE (100) is connected to theaccess network that provides connectivity to the MSGin5G server (16).The MSGin5G UE (200) does not have a connection to the access networkthat provides connectivity to the MSGin5G server (16). The MSGin5Gclient (20B) has registered with the MSGin5G server (16) using theMSGin5G UE (100) which is acting as a message gateway device.

At operation 1101, the MSGin5G client (10B) receives either the groupmessage or the point-to-point message or the application-to-pointmessage from the MSGin5G server (16) for the MSGin5G client (20B) forwhich the MSGin5G client (10B) is acting as the message gateway deviceas specified in clause 8.3.3 of 3GPP TS 23.554. The MSGin5G client (10B)performs reassembly of the received message that is segmented. TheMSGin5G client (10B) may also perform a segment recovery procedure torecover missing segments.

At operation 1102, upon successfully receiving the message for theMSGin5G client (20B), the MSGin5G client (10B) sends the MSGin5G messagereceived request to the MSGin5G client (20B). The information elementsof the MSGin5G message received request are defined in Table 6.

TABLE 6 MSGin5G message received request Information element StatusDescription Originator MSGin5G M The identity of the MSGin5G client whoservice ID initiated the message. Group ID O The identifier of theMSGin5G Group to which the message is sent Message ID M Uniqueidentifier of this message Disposition Type O Indicates the dispositiontype expected from the receiver (i.e., delivered) as specified in GroupMessage Request received from originating MS client Application ID OIdentifies the application for which the payload is intended asspecified in Group Message Request received from originating MSGin5Gclient Payload M Payload of the message Priority Type O Applicationpriority level requested for this message as specified in Group MessageRequest received from originating MSGin5G client.

At operation 1103, upon successfully receiving the message, the MSGin5Gclient (20B) sends the MSGin5G send message response to the MSGin5Gclient (10B). At operation 1104, if the delivery report is required, theMSGin5G client (20B) sends the delivery report to the MSGin5G client(10B). At operation 1105, upon receiving the delivery report, theMSGin5G client (10B) sends the delivery report to the MSGin5G server(16).

FIG. 12 is a signaling diagram illustrating registration of theconstrained device (200) with the unconstrained UE (100) for using thegateway functionality, according to an embodiment of the disclosure.

Referring to FIG. 12, the signaling flow for registration of theapplication client (20A) on the MSGin5G UE (200) with the MSGin5G client(10B) to use the MSGin5G UE (100) as the gateway device. Consider, theMSGin5G UE (100) is connected to the access network that providesconnectivity to the MSGin5G server (16). The MSGin5G UE (100) isconfigured with information to recognize and authorize the MSGin5G UE(200). The MSGin5G UE (200) does not have the access network connectionto connect with the MSGin5G server (16). The MSGin5G UE (200) hasdiscovered that the MSGin5G UE (100) is having connectivity to theMSGin5G server (16) and offers the gateway functionality.

At operation 1201, the application client (20A) on the MSGin5G UE (200)registers with the MSGin5G client (10B) in MSGin5G UE (100) to requestthe MSGin5G client (10B) to act as the gateway UE. The request messageincludes information elements as specified in Table 7.

TABLE 7 Information elements for request for registration to use gatewayfunctionality Information element Status Description Layer-2 ID MLayer-2 identity of MS Gin5G UE (100) Application ID M Application ID ofthe application client on MSGin5G UE (200)

At operation 1202, upon receiving the request from the applicationclient (20A), the MSGin5G client (10B) rejects the request forregistration to use the gateway functionality based on the localcondition (like available power or connectivity to access network or anyother reason outside the scope of 3GPP). If the MSGin5G client (10B)decides to reject the request for registration to use gatewayfunctionality, then proceed to operation 1204. Otherwise, the MSGin5Gclient (10B) authorize the application client (20A), on the MSGin5G UE(200) to use the gateway functionality, and the MSGin5G client (10B)stores the mapping between the application ID and the layer-2 ID of theMSGin5G UE (200). If authorization fails, then proceed to the operation1204. The MSGin5G client (10B) may have a list of MSGin5G UEs configuredthat can use the gateway functionalities or may send authorizationmessage to the MSGin5G server (16) to check whether the MSGin5G UE (200)is authorized to use the gateway functionality.

At operation 1203, the MSGin5G client (10B) updates its own registrationwith MSGin5G server (16) to include the application ID. At operation1204, the MSGin5G client (10B) sends response to the application client(20A). If the MSGin5G client (10B) decided to reject the request forregistration to use the gateway functionality or if authorization failsas in operation 1202, the MSGin5G client (10B) sends the failureresponse to the application client (20A). Otherwise, the MSGin5G client(10B) sends the success response to the application client (20A). TheMSGin5G client (10B) may act as the gateway device for multipleconstrained devices at the same time. In an embodiment, upon receivingthe MSGin5G message, the MSGin5G UE (100) uses the mapping created attime of successful registration to identify target constrained deviceand sends message to the target constrained device. In anotherembodiment, the procedure is also applicable for mission criticalgateway, where non-3GPP devices, which cannot host mission criticalclients, act as the MSGin5G UE (200), and a mission critical gateway UEact as the MSGin5G UE (100).

FIG. 13 is a signaling diagram illustrating the deregistration of theconstrained device (200) with the unconstrained UE (100) fordiscontinuing usage of the gateway functionality, according to anembodiment of the disclosure.

Referring to FIG. 13, consider, the MSGin5G UE (100) is connected to theaccess network that provides connectivity to the MSGin5G server (16).The MSGin5G UE (200) is successfully connected to MSGin5G UE (100)acting as the gateway device. At operation 1301, the application client(20A) on the MSGin5G UE (200) deregisters with the MSGin5G client (10B)in MSGin5G UE (100) to discontinue usage of the gateway functionality ofthe MSGin5G UE (100). The request message includes information elementsas specified in Table 7. At operation 1302, upon receiving the requestfrom the application client (20A), the MSGin5G client (10B) removes themapping between the application ID and the layer-2 ID of the MSGin5G UE(200), and updates its own registration with the MSGin5G server (16) toupdate the application ID. At operation 1303, the MSGin5G client (10B)sends the response to the application client (20A) on the MSGin-5G UE(200).

The proposed method is used for constrained UE (200) to register withthe unconstrained UE (100) to enable and use the gateway functionality.Further, the proposed method is used for the constrained UE (200) toderegister with the unconstrained UE (100) to discontinue use of thegateway functionality. Furthermore, the proposed method is used for thegateway device to find the target constrained device (200) for whom themessage has been received.

The foregoing description of the specific embodiments will so fullyreveal the general nature of the embodiments herein that others can, byapplying current knowledge, readily modify and/or adapt for variousapplications such specific embodiments without departing from thegeneric concept, and, therefore, such adaptations and modificationsshould and are intended to be comprehended within the meaning and rangeof equivalents of the disclosed embodiments. It is to be understood thatthe phraseology or terminology employed herein is for the purpose ofdescription and not of limitation.

While the disclosure has been shown and described with reference tovarious embodiments thereof, it will be understood by those skilled inthe art that various changes in form and details may be made thereinwithout departing from the spirit and scope of the disclosure as definedby the appended claims and their equivalents.

What is claimed is:
 1. A method for communication of a constrained UserEquipment (UE) with a Message in Fifth Generation (MSGin5G) serverproviding a MSGin5G service in an Internet-of-Things (IoT) network, themethod comprising: receiving, by an unconstrained UE, a registrationrequest comprising a security credential of the constrained UE from theconstrained UE, wherein the unconstrained UE has access to the MSGin5Gserver and the constrained UE does not have access to the MSGin5Gserver; determining, by the unconstrained UE, whether the constrained UEis authorized based on the security credential; and performing, by theunconstrained UE, a registration of the constrained UE with theunconstrained UE for communication of the constrained UE with theMSGin5G server based on authorization of the constrained UE.
 2. Themethod as claimed in claim 1, wherein the receiving, by theunconstrained UE, the registration request comprising the securitycredential of the constrained UE from the constrained UE, comprises:identifying, by the constrained UE, that the unconstrained UE isconnected to the MSGin5G server; and sending, by the constrained UE, theregistration request comprises the security credentials of theconstrained UE to the unconstrained UE.
 3. The method as claimed inclaim 1, wherein the unconstrained UE and the constrained UE communicateeach other through a MSGin5G-6 interface.
 4. The method as claimed inclaim 1, wherein the performing, by the unconstrained UE, of theregistration of the constrained UE with the unconstrained UE forcommunication of the constrained UE with the MSGin5G server based onauthorization of the constrained UE, comprises: determining, by theunconstrained UE, whether a local condition of the unconstrained UE tocommunicate with the MSGin5G server matches a threshold condition; andperforming, by the unconstrained UE, one of: discarding the registrationrequest of the constrained UE, in response to determining that theconstrained UE is not authorized based on the security credential, andthe local condition of the unconstrained UE does not match the thresholdcondition, and registering the constrained UE with the unconstrained UEby storing a mapping between information of the constrained UE and alayer-2 ID of the constrained UE, and enabling a gateway functionalityof the unconstrained UE to operate the unconstrained UE as a gatewaydevice for communication of the constrained UE with the MSGin5G server,in response to determining that the constrained UE is authorized basedon the security credential, and the local condition of the unconstrainedUE matches the threshold condition; and sending, by the unconstrainedUE, a registration response to the constrained UE.
 5. The method asclaimed in claim 4, wherein the information of the constrained UEcomprises an application Identity (ID) of an application client on theconstrained UE.
 6. The method as claimed in claim 4, wherein the localcondition comprises at least one of an available power at theunconstrained UE and a network connectivity to access the MSGin5Gserver.
 7. The method as claimed in claim 4, wherein the sending, by theunconstrained UE, of the registration response to the constrained UE,comprises: sending, by the unconstrained UE, a registration successresponse to the constrained UE, in response to registering theunconstrained UE with the constrained UE; and sending, by theunconstrained UE, a registration failure response to the constrained UE,in response to discarding the registration request of the constrainedUE.
 8. The method as claimed in claim 4, further comprising: receiving,by the unconstrained UE, a deregistration request from the constrainedUE, wherein the constrained UE is registered to the unconstrained UE;performing, by the unconstrained UE, a deregistration of the constrainedUE with the unconstrained UE by removing the mapping between theinformation of the constrained UE and the layer-2 ID of the constrainedUE; sending, by the unconstrained UE, a deregistration response to theconstrained UE; and disabling, by the unconstrained UE, the gatewayfunctionality of the unconstrained UE when none of registered devicesare using the unconstrained UE as a gateway device.
 9. The method asclaimed in claim 1, further comprising: receiving, by the unconstrainedUE, a request for sending a MSGin5G message to the MSGin5G server fromthe constrained UE; determining, by the unconstrained UE, whether alocal condition of the unconstrained UE to communicate with the MSGin5Gserver matches a threshold condition; performing, by the unconstrainedUE, one of: sending the MSGin5G message as one of a point-to-pointmessage or a group message to the MSGin5G server, in response todetermining that the local condition of the unconstrained UE matches thethreshold condition, and discarding the request for sending the MSGin5Gmessage to the MSGin5G server, and sending a registration failureresponse to the constrained UE, in response to determining that thelocal condition of the unconstrained UE does not match the thresholdcondition; and sending, by the unconstrained UE, a response of sendingthe MSGin5G message to the constrained UE.
 10. The method as claimed inclaim 9, wherein the sending, by the unconstrained UE, of the responseof sending the MSGin5G message to the constrained UE, comprises:sending, by the unconstrained UE, a success response of sending theMSGin5G message to the constrained UE, in response to sending theMSGin5G message to the MSGin5G server; and sending, by the unconstrainedUE, a failure response of sending the MSGin5G message to the constrainedUE, in response to discarding the request for sending the MSGin5Gmessage to the MSGin5G server.
 11. The method as claimed in claim 9,wherein the local condition comprises at least one of an available powerat the unconstrained UE, a network connectivity to access the MSGin5Gserver, or a maximum allowed packet size of the MSGin5G message.
 12. Themethod as claimed in claim 9, further comprising: receiving, by theunconstrained UE, a delivery report from the MSGin5G server, when adelivery status is enabled while sending the MSGin5G message to theMSGin5G server; and sending, by the unconstrained UE, the deliveryreport to the constrained UE.
 13. The method as claimed in claim 1,further comprising: receiving, by the unconstrained UE, a messageincluding one of a group message, a point-to-point message, or anapplication-to-point message from the MSGin5G server; performing, by theunconstrained UE, a reassembly of the received message when the receivedmessage is segmented, wherein the unconstrained UE performs a segmentrecovery of the received message when at least one segment is missing inthe received message; sending, by the unconstrained UE, a MSGin5Gmessage received request to the constrained UE, wherein the MSGin5Gmessage received request comprises an originator address, a group ID, apayload of the received message, a delivery status, and a priority type;and receiving, by the unconstrained UE, a message received response fromthe constrained UE when the MSGin5G message received request is receivedat the constrained UE.
 14. The method as claimed in claim 13, furthercomprising: receiving, by the unconstrained UE, a message deliverystatus from the constrained UE, when a delivery status is enabled in theMSGin5G message received request and the MSGin5G message receivedrequest is received at the constrained UE; and sending, by theunconstrained UE, a delivery report to the MSGin5G server.
 15. A methodfor communication of a constrained User Equipment (UE) with a Message inFifth Generation (MSGin5G) server) providing a MSGin5G service in anInternet-of-Things (IoT) network, the method comprising: receiving, byan unconstrained UE having access to the MSGin5G server, a registrationrequest from a constrained UE, wherein the registration requestcomprises a security credential required for the constrained UE toregister to the MSGin5G server; determining, by the unconstrained UE, alocal condition at the unconstrained UE for accepting or rejecting thereceived registration request; and performing, by the unconstrained UE,a registration for the constrained UE with the MSGin5G server when theregistration request is accepted based on the local condition.
 16. Themethod as claimed in claim 15, wherein the local condition comprises atleast one of an available power at the unconstrained UE, or a networkconnectivity to access the MSGin5G server.
 17. The method as claimed inclaim 15, further comprising: accepting, by the MSGin5G server, theregistration request from the unconstrained UE on behalf of theconstrained UE based on the received security credential; and storing,by the MSGin5G server, a mapping of the unconstrained UE acting as agateway device to the constrained UE.
 18. The method as claimed in claim15, further comprising: sending, by the unconstrained UE, a registrationresponse message to the constrained UE indicating success or failure ofthe registration with the MSGin5G server, wherein the registrationresponse message comprises a reason for registration failure in case ofthe failure of the registration, and wherein the registration responsemessage comprises a MSGin5G service ID in case of the success of theregistration.
 19. An unconstrained User Equipment (UE) for communicationof a constrained UE with a Message in Fifth Generation (MSGin5G) serverproviding a MSGin5G service in an Internet-of-Things (IoT) network, theunconstrained UE comprising: a memory; a processor; and a gatewaycontroller, coupled to the memory and the processor, configured to:receive a registration request comprises a security credential of theconstrained UE from the constrained UE, wherein the unconstrained UEhave access to the MSGin5G server and the constrained UE do not haveaccess to the MSGin5G server, determine whether the constrained UE isauthorized based on the security credential, and perform a registrationof the constrained UE with the unconstrained UE for communication of theconstrained UE with the MSGin5G server based on authorization of theconstrained UE.
 20. An unconstrained User Equipment (UE) forcommunication of a constrained UE with a Message in Fifth Generation(MSGin5G) server providing a MSGin5G service in an Internet-of-Things(IoT) network, the unconstrained UE comprising: a memory; a processor;and a gateway controller, coupled to the memory and the processor,configured to: receive a registration request from a constrained UE,wherein the registration request comprises a security credentialrequired for the constrained UE to register to the MSGin5G server,determine a local condition at the unconstrained UE for accepting orrejecting the received registration request, and performing aregistration for the constrained UE with the MSGin5G server when theregistration request is accepted based on the local condition.